Distributed global load-balancing system for software-defined data centers

ABSTRACT

The disclosure herein describes a system for providing distributed global server load balancing (GSLB) over resources across multiple data centers. The system includes a directory group comprising one or more directory nodes and a plurality of GSLB nodes registered to the directory group. A respective GSLB node is configured to provide GSLB services over a respective portion of the resources. A directory node includes a domain name system (DNS) query-receiving module configured to receive a DNS query from a client, a node-selecting module configured to select from the plurality of GSLB nodes a first GSLB node based at least on the DNS query, and a DNS query-responding module configured to respond to the DNS query to the client using an address of the selected first GSLB node, thereby facilitating the selected first GSLB node in performing GSLB while resolving the DNS query.

BACKGROUND

Global Server Load Balancing (GSLB) based on Domain Name System (DNS) is an essential technology used in modern day data centers. GSLB allows a service provider to distribute workloads across multiple data centers. As a result, GSLB facilitates more evenly distributed traffic, business continuance, and disaster recovery. GSLB devices can be deployed with each data center and registered with an upper-level DNS server. These GSLB devices are typically synchronized with respect to the data centers' service state. The GSLB devices can resolve DNS queries (e.g., by returning the IP address of a selected data center) based on defined load-balancing policies, either static or dynamic. In addition, the GSLB devices typically monitor the health status of all the services independently. However, when a customer maintains a large number of data centers, registering a corresponding number of GSLB devices with a third-party DNS service can be difficult. It can also be costly, both in terms of bandwidth consumption and computation, to synchronize the data-center state information across different GSLB devices. As the number of data centers increases, the associated high capital expenditure (CapEx) and operational expenditure (OpEx), increased management and configuration overhead, scalability issues, and resilience issues can make the current GSLB solutions prohibitively expensive.

Furthermore, the emergence of software-defined data centers (SDDCs) which facilitates a significantly increased number of virtual data centers can exacerbate the aforementioned problems. SDDC expands beyond server virtualization, and facilitates virtualization of a wide variety of data center resources and services by operating data centers on community hardware rather than dedicated hardware devices SDDC is capable of providing customers with virtual data centers (VDC), which require network isolation, large layer 2 broadcast domains, dedicated network services, and greater scalability. A single hardware-based GSLB device dedicated to a physical data center might not be sufficient to meet such requirements.

In an SDDC environment, a physical data center (also known as a site) may support multiple tenants, each demanding dedicated GSLB service. As the number of sites increases and the number of customers being supported also increases, a large number of GSLB devices (which are likely to be virtualized) are needed. For example, for the virtual desktop application, the number of data center sites may exceed 50, and the number of GSLB devices needed per site may be even larger, such as hundreds or thousands. Current GSLB technologies are not suited for scaling up because registering such a large number (>1000) of GSLB devices to upper-level DNS servers is nearly impossible. In addition, heartbeat monitoring, collaboration, and synchronization among a large number of GSLB devices can be extremely troublesome, especially over the Internet.

SUMMARY

The disclosure herein describes a system for providing distributed global server load balancing (GSLB) over resources across multiple data centers. The system includes a directory group comprising one or more directory nodes and a plurality of GSLB nodes registered to the directory group. A respective GSLB node is configured to provide GSLB services over a respective portion of the resources. A directory node includes a domain name system (DNS) query-receiving module configured to receive a DNS query from a client, a node-selecting module configured to select from the plurality of GSLB nodes a first GSLB node based at least on the DNS query, and a DNS query-responding module configured to respond the DNS query to the client using an address of the selected first GSLB node, thereby facilitating the selected first GSLB node in performing GSLB while resolving the DNS query.

BRIEF DESCRIPTION OF FIGURES

FIG. 1 presents a diagram illustrating an exemplary distributed GSLB system.

FIG. 2 presents a table illustrating the exemplary metadata maintained by a GSLB directory node.

FIG. 3 presents a table illustrating the exemplary metadata maintained by a general GSLB node.

FIG. 4 presents a flowchart illustrating an exemplary process of registering a general GSLB node to a GSLB directory group.

FIG. 5 presents an exemplary workflow of responding client DNS queries.

FIG. 6 presents a diagram illustrating the exemplary architecture of a GSLB directory node and a general GSLB node.

FIG. 7 illustrates an exemplary computer system for providing distributed GSLB services.

In the figures, like reference numerals refer to the same figure elements.

DETAILED DESCRIPTION

The following description is presented to enable any person skilled in the art to make and use the embodiments, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present disclosure. Thus, the present invention is not limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.

The present disclosure describes a system and a method that provide distributed GSLB services to meet the requirements of high scalability, high performance, and high availability in SDDC. More specifically, the GSLB devices include two layers: a directory layer and a service layer. The directory layer includes a small number of GSLB directory nodes (GslbDirNodes), and the service layer includes a large number of general GSLB nodes (GslbNodes). The GSLB directory nodes maintain the metadata of all general GSLB nodes, and provide mapping between global IPs (which represent different services) and the general GSLB nodes (each may provide GSLB services for a number of global IPs). In addition, the GSLB directory nodes monitor the health of all general GSLB nodes. In one embodiment, the GSLB directory nodes receive heartbeat messages from the general GSLB nodes. During operation, the GSLB directory nodes direct client DNS requests to an appropriate general GSLB node, which serves the final DNS queries from clients. A general GSLB node holds GSLB configuration for the domains (or global IPs) it supports as well as runtime data, such as a round-trip time (RTT) cache and a persistence cache, and monitors the health of the services. The RTT cache enables the general GSLB node to run RTT-based GSLB algorithm much more quickly, because no RTT measurement is needed if the RTT data associated with a particular client has been cached at the GSLB node. The number of GSLB directory nodes is kept small to minimize the traffic need for state synchronization among these directory nodes. On the other hand, there may be hundreds, even thousands, of general GSLB nodes in the system.

FIG. 1 presents a diagram illustrating an exemplary distributed GSLB system. In FIG. 1, distributed GSLB system 100 includes a directory layer 104 and a service layer 106. Directory layer 104 includes a number of GSLB directory nodes, such as GslbDirNodes 108, 110, and 112. Service layer 106 includes a number of general GSLB nodes, such as GslbNodes 114, 116, 118, and 120.

The few GSLB directory nodes (in the example shown in FIG. 1, there are three GslbDirNodes) are deployed across the multiple geographically dispersed sites, and form a directory group (GslbDirGroup). In the environment of multi-tenant data centers, each tenant can establish its own GslbDirGroup. Note that the number of sites can be much larger than the number of the GSLB directory nodes. For example, to provide virtual desktop services for customers across the globe, over 50 sites may be needed. These GslbDirNodes are registered with DNS providers as the authoritative name server for the fully qualified domain names (FQDNs) of the service. For example, when a customer tries to log on to the virtual desktop service, the DNS query for the service is directed to one of the GSLB directory nodes by the upper-layer DNS server. In one embodiment, the GslbDirNodes register their virtual IPs to the DNS providers as the authoritative name server for the virtual desktop service such that client DNS queries will be recursively directed to these GslbDirNodes. Note that the DNS response may list all GSLB directory nodes within the directory group, and the client can choose to send DNS queries to any one of the GSLB directory nodes. The directory nodes do not respond to the client DNS queries directly, but direct the DNS queries to proper general GSLB nodes based on the domain name included in the DNS query, because different GSLB nodes may support different domain names. In a further embodiment, when there are multiple GSLB nodes supporting the queried domain name, the directory node may select a GSLB node based on the physical proximity to the client.

As shown in FIG. 1, multiple GSLB directory nodes are spread across Internet 102. Resilience can be supported within a GSLB directory group. To do so, persistent connections among the GSLB directory nodes within a directory group are maintained to sync-up state data among all GSLB directory nodes. Note that the GSLB directory nodes do not maintain any runtime data. Hence, synchronization can be simple. In one embodiment, the directory nodes exchange heartbeat messages among each other. Because these directory nodes are fully synchronized, if one fails, the other surviving ones can provide the same services. The registration between the GSLB directory group and the DNS server changes only when membership within the directory group changes, i.e., only when a GSLB directory node is added or deleted. Because the number of directory node is low, such occurrences tend to be rare. On the other hand, no change to the DNS registration is required when a general GSLB node is added or removed by the data center tenants. Note that the GslbDirNodes can be deployed in existing virtual data centers or be placed in dedicated locations across the Internet. It is also possible to place a GslbDirNode and a general GSLB node in the same physical enclosure, such as a server box.

In one embodiment, each GslbDirNode maintains the metadata of all general GSLB nodes registered to the GslbDirGroup and monitors the health of these general GSLB nodes. FIG. 2 presents a table illustrating the exemplary metadata maintained by a GSLB directory node. In the example shown in FIG. 2, each GslbDirNode maintains two records: a global IP mapping table and a list of general GSLB nodes within the GSLB namespace. The global IP mapping table provides mappings between the global IPs (which can be virtual IPs) and the individual GSLB nodes that support these global IPs. In this disclosure, a global IP can be a virtual IP address that maps a domain name (such as a FQDN) to one or more pools of servers that host the domain's content, such as a website, an e-commerce site, or a content delivery network. Note that such a mapping is often many-to-many with a general GSLB node being mapped to multiple global IPs (because a single site may provide services for multiple domain names), and a particular global IP being mapped to multiple GSLB nodes (because a single service or a domain name may be supported at multiple sites). In FIG. 2, Global_IP_1 is supported by both GslbNode_1 and GslbNode_2, and Global_IP_2 is supported by both GslbNode_1 and GslbNode_3, meaning that a DNS query for domain name Global_IP_1 can be directed to either GslbNode_1 or GslbNode_2, and a DNS query for domain name Global_IP_2 can be directed to GslbNode_1 or GslbNode_3.

The other record maintained by the GslbDirNode is the GSLB namespace, which includes all general GslbNodes registered to the GSLB directory group. In one embodiment, one entry is kept for each general GSLB node. Each entry includes the name of the general GSLB node, its IP address, its status, its location, and the identifications of its one or more replica nodes. During operation, the GslbDirNode can use the namespace record to balance queries among all GSLB nodes. For example, the location information maintained in the metadata enables the GslbDirNode to identify a GSLB node that is geographically close to the client sending the DNS query, and the status information enables the GslbDirNode to determine the availability of a GSLB node.

The metadata associated with a general GSLB node (GslbNode) is reported to the GslbDirNodes when the GslbNode registers itself with the GslbDirGroup. In one embodiment, each GslbNode holds GSLB configurations for the sites it manages. In addition, runtime data, such as the RTT cache and the persistence cache, may also be maintained by the GslbNode. In one embodiment, one GslbNode is deployed at each virtual data center, and the GslbNode can be configured to run a normal GSLB service across multiple sites. For example, a GslbNode deployed in the Beijing VDC may manage server pools located in both the Beijing VDC and the Tokyo VDC. However, unlike the conventional GSLB system, the general GSLB nodes in the distributed system do not communicate or synchronize with other general GSLB nodes, with the exception of sending replica information to selected replica nodes. Instead of maintaining synchronization with other GslbNodes, a GslbNode only communicates with the GslbDirNodes. In one embodiment, a GslbNode registers itself to a GslbDirGroup (which can include a few GslbDirNodes) and reports its metadata to one of the GslbDirNodes. In addition, the GslbNode periodically sends heartbeat messages to the GslbDirNodes, and the GslbDirNodes may issue commands (such as replica commands) to the GslbNode.

FIG. 3 presents a table illustrating the exemplary metadata maintained by a general GSLB node. The metadata for a general GSLB node includes its ID (GslbNode_ID), its IP address, and its physical location. In addition, the metadata includes the identifications of replica nodes of the current GslbNode. In the example shown in FIG. 3, the replica nodes for the current GslbNode are GslbNode_4 and GslbNode_5. The metadata also includes global IPs supported by this GslbNode, and server pools and sites managed by this GslbNode. These server pools and sites are bound to the GslbNode during configuration of the GslbNode. Note that each server pool may include multiple virtual IPs (VIPs), with each VIP associated with a number of physical servers. The sites represent the virtual data centers that are bound to the GslbNode. In one embodiment of the present invention, one GslbNode is deployed at each virtual data center, and can be bound to multiple server pools and multiple sites. Note that for SDDCs the boundaries of the server pools and the data center sites may cross each other.

When a new general GSLB node is added, it registers itself with the GSLB directory group. The registration process includes reporting metadata and establishing replicas. FIG. 4 presents a flowchart illustrating an exemplary process of registering a general GSLB node to a GSLB directory group. When a general GSLB node is added, during startup, the new GSLB node establishes a connection to one of the GSLB directory nodes within the directory group (operation 402), and sends its metadata to the GSLB directory node, which stores the metadata in its record tables (operation 404). In one embodiment, the metadata includes, but is not limited to: the ID of the GSLB node, its IP address, a set of global IPs (or domain names) supported by the GSLB node, and the location of the GSLB node. The new GSLB node then receives the directory node ID (GslbDirNode_ID) (operation 406). Subsequently, the GSLB directory node determines one or more replica nodes for the newly added GslbNode, and the newly added GslbNode receives replica commands from the directory node (operation 408). In one embodiment, the replica commands specify the node IDs of the replica nodes. Note that the replica nodes may be randomly selected or be selected based on physical proximity. Upon receiving the replica commands, the newly added GSLB node subscribes to the one or more replica nodes to receive replica data (operation 410). In one embodiment, the replica data includes the metadata maintained at a particular GSLB node and the runtime cache data. After receiving the replica data, the newly added GSLB data can act as a backup to the replica nodes. If one of the replica nodes fails, DNS queries directed to that replica node may be directed to this newly added GSLB node. The newly added GSLB node can also act as a primary node by publishing its replica data (operation 412). In one embodiment, each GSLB node periodically publishes its replica data to allow the replica nodes to update the received replica data regularly. Note that, although during registration the GSLB node only submits its metadata to one of the GSLB directory nodes, because all directory nodes within the GSLB directory group maintain state synchronization, the other directory nodes will receive a copy of the metadata of the newly added GSLB data. There is no need to notify the DNS server of changes regarding the addition/removal of a GSLB node. Also, note that, because there are only a few GSLB directory nodes (often an odd number), the addition of a new GSLB node does not generate excessive network traffic. On the other hand, when the GSLB configuration changes at the GSLB node, such as addition or removal of a server or pool of servers, such a configuration change only affects the corresponding GSLB node. There is no need for the GSLB node to synchronize its status with the large number of other GSLB nodes. As a result, no excessive traffic will be generated because of the GSLB configuration change.

After a GSLB node is registered with the GSLB directory group, it may receive client DNS queries directed by the GslbDirNodes. The GslbNode also periodically sends heartbeat messages to at least one of the GslbDirNodes to confirm that it is operating. In one embodiment, the GslbNode periodically sends the heartbeat messages to the GslbDirNode it is registered to. The heartbeat messages can carry runtime statistics of the GslbNode such that the GslbDirNodes within the GslbDirGroup can balance DNS queries among all GSLB nodes based on the runtime statistics associated with the GSLB nodes. While in operation, if one GslbNode is down, the GslbDirNode will select another GslbNode to serve the DNS queries originally directed to the failed GslbNode. In one embodiment, the GslbDirNode may select one of the replica nodes of the failed GslbNode to serve the DNS queries. Note that the replica information is maintained by the directory nodes. In a different embodiment, the GslbDirNode may select a GslbNode that is not a replica of the failed GslbNode. In such a situation, the GslbDirNode will send a command to a replica of the failed GslbNode, requesting the replica node to send replica data to the selected GslbNode.

FIG. 5 presents an exemplary workflow of responding client DNS queries. During operation, a DNS query from a client 502 is directed to an appropriate DNS server 504 (operation 522). For example, a DNS query www.abc.com can be recursively directed to the “abc.com” DNS server. DNS server 504 responds with a DNS response that indicates the canonical name (CNAME) of the queried name and the name server to which the DNS request should be directed (operation 524). Note that, to provide GSLB services, the GSLB directory nodes are registered with the DNS server as the authoritative name server for the name space “abc.com.” In the example shown in FIG. 5, a GslbDirGroup 506 is registered with the DNS server as the authoritative name server for the name space “abc.com.” GslbDirGroup 506 can include a number of GSLB directory nodes, such as a GslbDirNode_1 508, a GslbDirNode_2 510, and a GslbDirNode_3 512.

In FIG. 5, the DNS response sent from DNS server 504 to client 502 can be “CNAME=gslb.www.abc.com, NS=dir1.gslb.www.abc.com, dir2.gslb.www.abc.com,” which identifies GslbDirNode_1 508 and GslbDirNode_2 510 as the name servers for the namespace “abc.com.” Subsequently, client 502 sends the DNS query using the CNAME (gslb.www.abc.com) to one of the identified name servers, such as GslbDirNode_1 508 (operation 526). GslbDirNode_1 508 identifies a GslbNode among all registered GslbNodes (such as a GslbNode 514 and a GslbNode 516) that supports the domain name and is closest to client 502 based on the DNS query and the IP location of client 502 and sends a DNS response to client 502, which indicates the identified GslbNode as the name server for the namespace gslb.www.abc.com (operation 528). In the example shown in FIG. 5, GslbDirNode_1 508 may determine that both GslbNode 514 and GslbNode 516 support the queried domain name (gslb.www.abc.com). However, based on the IP of client 502, GslbDirNode_1 508 may return GslbNode 514 because it is located at a virtual data center (VDC) in Tokyo and is closer to client 502.

Subsequently, client 502 submits the DNS query (gslb.www.abc.com) to GslbNode 514 located in the Tokyo VDC (operation 530), and GslbNode 514 responds to the DNS query with the VIP that is available and closest to client 502 (operation 532). Note that the VIP may represent a group of physical servers. Also note that if GslbDirNode_1 508 determines that GslbNode 514 is not operating (based on the absence of normal heartbeat messages), GslbDirNode_1 508 may identify the replica for GslbNode 514, which can be GslbNode 516 located at a VDC in Palo Alto, and respond to the DNS query from client 502 with GslbNode 516. In such a situation, client 502 will send its subsequent DNS query to GslbNode 516. This arrangement provides intelligent failover without overwhelming the network with traffic. In other words, the detection of a failed GslbNode does not generate traffic for state synchronization among possibly hundreds or thousands of GslbNodes. The directory node can seamlessly redirect DNS queries to existing replicas of the failed GslbNode. All other GslbNodes need not be notified.

FIG. 6 presents a diagram illustrating the exemplary architecture of a GSLB directory node and a general GSLB node. In FIG. 6, GSLB directory node 600 includes a DNS proxy 602, a directory engine 604, a node manager 606, and a directory database 608. General GSLB node 610 includes a node client 612, a replica engine 614, a DNS proxy 616, a GSLB daemon 618, and a GSLB configuration database 620.

Within GSLB directory node 600, DNS proxy 602 is responsible for handling client DNS queries. During operation, upon receiving a DNS query from the client, DNS proxy 602 may determine the location of the client based on the client's IP address and perform a lookup in directory database 608 (which stores metadata of all registered GSLB nodes) to identify a general GSLB node that supports the queried domain name and is closest to the client. In a further embodiment, DNS proxy 602 may run certain balancing algorithms in order to identify a general GSLB node that can best serve the client DNS query. In addition to location, the balancing algorithm may take into consideration the availability and the health status of other qualified general GSLB nodes, and the traffic condition of the current network.

DNS directory engine 604 is responsible for state synchronization among all GSLB directory nodes within the same GSLB directory group. All GSLB directory nodes within the same GSLB directory group are fully synchronized. The GSLB node metadata (which is stored in directory database 608 and is associated with all registered GSLB nodes) is shared among all GSLB directory nodes. In one embodiment, the synchronization among the directory nodes may be performed periodically. In one embodiment, the synchronization is only performed when change (such as addition or removal of a registered GSLB node) occurs on one of the directory nodes. In addition, directory engine 604 is also responsible for handling failover cases. When a GSLB node failure is detected, directory engine 604 looks up directory database 608 for replica nodes of the failed GSLB node and syncs up with other directory nodes regarding the health status of the failed node.

Node manager 606 is responsible for managing communications between the general GSLB node and the GSLB directory node. More specifically, node manager 606 handles registration of the GSLB nodes, and receives heartbeat messages and status reports from the GSLB nodes. During the registration process, node manager 606 receives metadata from the GSLB node and stores the metadata in directory database 608. Moreover, node manager 606 may send commands to the GSLB node. In one embodiment, node manager 606 may send a replica command prompting a GSLB node to send replica data to a different GSLB node.

Node client 612 located within general GSLB node 610 interfaces with node manager 606 located within GSLB directory node 600. More specifically, node client 612 is responsible for registering general GSLB node 610 to GSLB directory node 600. During registration, node client 612 submits metadata associated with general GSLB node 610 to node manager 606. In addition, node client 612 receives commands from GSLB directory node 600 and processes the received commands. Replica engine 614 is responsible for replicating runtime state (such as the RTT cache) as well as GSLB node metadata to selected GSLB nodes.

GSLB daemon 618 performs normal load-balancing services, including running complex load-balancing algorithms (such as RTT-based GSLB algorithms) and monitoring the service health. In one embodiment, GSLB daemon 618 determines which server cluster (represented by a virtual IP) can serve the client request the best based on the RTT data and the performance of the server clusters. Note that runtime data used for running the load-balancing algorithm may be cached. DNS proxy 616 handles client DNS queries and responds to the queries using the load-balancing results from GSLB daemon 618. GSLB configuration database 620 stores the metadata associated with general GSLB node 610, including the GSLB load-balancing configuration for the VDC on which general GSLB node 610 is located.

Note that compared with the conventional GSLB system which relies on centralized GSLB devices to perform DNS load balancing globally, embodiments of the present invention rely on distributed GSLB nodes to perform the DNS load balancing. The GSLB directory nodes perform the first level of global IP mapping and load balancing, which is simple and fast enough to get high RPS (requests per second). Note that this first level load balancing does not involve running complex GSLB algorithms. The GSLB directory nodes then distribute the client DNS queries to the general GSLB nodes which perform the real GSLB load balancing, which can be time-consuming. Since the DNS queries are distributed, the aggregated RPS can be huge. In addition, because there is no need for collaboration among the general GSLB nodes, the system scalability can be high, where hundreds or even thousands of GSLB nodes can be deployed.

In general, within the distributed GSLB system, the data center resources that are to be load balanced are partitioned into multiple GSLB service zones with one GSLB node managing a GSLB service zone. A GSLB service zone can support a number of global IPs or name domains. Note that GSLB service zones may overlap because a global IP may be supported by multiple GSLB service zones. Similarly, the service zones may also overlap in terms of resources being managed because the same resource (such as a server pool) may support multiple domain names. The partitioning enables each GSLB node to provide GSLB services within its own service zone without the need to share the GSLB configuration information and runtime data with other GSLB nodes. Instead, the GSLB node only needs to report its service zoning information to GSLB directory nodes by informing the GSLB directory nodes which global IPs or name domains it supports. The GSLB directory node maintains mappings of the GSLB service zones, and distributes DNS queries to the various GSLB service zones based on the queried names and certain balancing policies. To enable intelligent failover, a GSLB node servicing a particular zone may replicate its GSLB configuration and runtime data at one or more other GSLB nodes, which can provide GSLB services for that zone in the event its own GSLB device fails. Compared with conventional GSLB systems where synchronization among all GSLB devices is required, backing up GSLB data only to a selected few nodes minimizes network traffic.

FIG. 7 illustrates an exemplary computer system for providing distributed GSLB services. In one embodiment, a computer and communication system 700 includes a processor 702, a memory 704, and a storage device 706. Memory 704 can include a volatile memory (e.g., RAM) that serves as a managed memory, and can be used to store one or more memory pools. Furthermore, computer system 700 can be coupled to a display device 714, a keyboard 716, and a pointing device 718. Storage device 706 can store an operating system 708, a distributed GSLB system 710, and data 712.

Distributed GSLB system 710 can include instructions, which when executed by computer system 700 can cause computer system 700 to perform methods and/or processes described in this disclosure. Specifically, distributed GSLB system 710 may include instructions for receiving and processing client DNS queries (DNS proxies 602 and 616). Further, distributed GSLB system 710 can include instructions for synchronization among directory nodes (directory engine 604) and instructions for registration and monitoring of the general GSLB nodes (node manager 606 and node client 612). Distributed GSLB system 710 can also include instructions for replicating GSLB node metadata (replica engine 614) and instructions for running a normal GSLB service (GSLB daemon 618).

Data 712 can include any data that is required as input or that is generated as output by the methods and/or processes described in this disclosure. Specifically, data 712 can store GSLB directory data and GSLB configuration at an individual GSLB node.

The data structures and code described in this detailed description are typically stored on a computer-readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system. The computer-readable storage medium includes, but is not limited to, volatile memory, non-volatile memory, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs), DVDs (digital versatile discs or digital video discs), or other media capable of storing computer-readable media now known or later developed.

The methods and processes described in the detailed description section can be embodied as code and/or data, which can be stored in a computer-readable storage medium as described above. When a computer system reads and executes the code and/or data stored on the computer-readable storage medium, the computer system performs the methods and processes embodied as data structures and code and stored within the computer-readable storage medium.

Furthermore, the methods and processes described above can be included in hardware modules. For example, the hardware modules can include, but are not limited to, application-specific integrated circuit (ASIC) chips, field-programmable gate arrays (FPGAs), and other programmable-logic devices now known or later developed. When the hardware modules are activated, the hardware modules perform the methods and processes included within the hardware modules.

The foregoing descriptions of embodiments of the present invention have been presented for purposes of illustration and description only. They are not intended to be exhaustive or to limit the present invention to the forms disclosed. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. Additionally, the above disclosure is not intended to limit the present invention. The scope of the present invention is defined by the appended claims. 

1-21. (canceled)
 22. A computer-implemented method for providing domain name system (DNS) query resolution across multiple data centers while reducing a number of authoritative name servers registered at a first DNS server and reducing volume of communication between authoritative name servers, comprising: at a directory node, second DNS server, registering the directory node, second DNS server with the first DNS server as an authoritative DNS name server for a domain name; receiving metadata for a plurality of third DNS servers to register the plurality of third DNS servers with the directory node, second DNS server; and using the received metadata to select a particular third DNS server from among the plurality of third DNS servers to use as a DNS name server in response to a particular domain name system (DNS) query for the domain name.
 23. The method of claim 22, wherein the metadata comprises one or more of: a name-server, third DNS server ID; an Internet Protocol (IP) address; a location; and one or more domain names supported by the respective third DNS server.
 24. The method of claim 23, wherein using the received metadata to select the particular third DNS server comprises looking up a mapping between the registered third DNS servers and domain names supported by the registered third DNS servers.
 25. The method of claim 23, wherein using the received metadata to select the particular third DNS server further comprises: determining a location of a client making the particular domain name system (DNS) query; determining locations of the plurality of third DNS servers; and determining health status of the plurality of third DNS servers.
 26. The method of claim 22, wherein the data centers include: physical data centers; and software-defined data centers.
 27. The method of claim 22, further comprising: sending, from the name-server-directory node, second DNS server, a replica command to one of the registered name-server, third DNS servers, wherein the replica command prompts the receiving name-server, third DNS server to send replica data to one or more different name-server, third DNS servers, wherein the replica data includes name-server, third DNS server configurations and runtime data associated with the receiving name-server, third DNS server, thereby enabling failover to the one or more different name-server, third DNS servers when the receiving name-server, third DNS server fails.
 28. The method of claim 22, wherein the name-server-directory node group comprises multiple state-synchronized name-server-directory node, second DNS servers, and wherein the multiple name-server-directory node, second DNS servers are placed at different data centers.
 29. The method of claim 22 wherein the name-server-directory node, second DNS servers are global server load balancing (GSLB) directory nodes.
 30. The method of claim 29, wherein the name-server, third DNS servers are GSLB nodes.
 31. The method of claim 30, wherein each GSLB node provides a load balancing service for a set of server clusters.
 32. A non-transitory machine readable medium storing a program for execution by at least one processing unit, the program for providing domain name system (DNS) query resolution across multiple data centers while reducing a number of authoritative name servers registered at an upper-level, first DNS server and while reducing volume of communication between authoritative name servers, the program comprising sets of instructions for: registering a particular name-server-directory node, second DNS server in a name-server-directory node group with the upper-level, first DNS server as an authoritative DNS name server for a domain name; at the particular name-server-directory node, second DNS server, registering a plurality of name-server, third DNS servers and receiving metadata for the registered name-server, third DNS servers; and using the received metadata to select a particular name-server, third DNS server from among the plurality of name-server, third DNS servers to use as a DNS name server in response to a particular domain name system (DNS) query for the domain name.
 33. The non-transitory machine readable medium of claim 32, wherein the metadata comprises one or more of: a name-server, third DNS server ID; an Internet Protocol (IP) address; a location; and one or more domain names supported by the respective name-server, third DNS server.
 34. The non-transitory machine readable medium of claim 33, wherein the set of instructions for using the received metadata to select the particular name-server, third DNS server comprises a set of instructions for looking up a mapping between the registered name-server, third DNS servers and domain names supported by the registered name-server, third DNS servers.
 35. The non-transitory machine readable medium of claim 33, wherein the set of instructions for using the received metadata to select the particular name-server, third DNS server further comprises sets of instructions for: determining a location of a client making the particular domain name system (DNS) query; determining locations of the plurality of name-server, third DNS servers; and determining health status of the plurality of name-server, third DNS servers.
 36. The non-transitory machine readable medium of claim 32, wherein the data centers include: physical data centers; and software-defined data centers.
 37. The non-transitory machine readable medium of claim 32, further comprising a set of instructions for: sending, from the name-server-directory node, second DNS server, a replica command to one of the registered name-server, third DNS servers, wherein the replica command prompts the receiving name-server, third DNS server to send replica data to one or more different name-server, third DNS servers, wherein the replica data includes name-server, third DNS server configurations and runtime data associated with the receiving name-server, third DNS server, thereby enabling failover to the one or more different name-server, third DNS servers when the receiving name-server, third DNS server fails.
 38. The non-transitory machine readable medium of claim 32, wherein the name-server-directory node group comprises multiple state-synchronized name-server-directory node, second DNS servers, and wherein the multiple name-server-directory node, second DNS servers are placed at different data centers.
 39. The non-transitory machine readable medium of claim 32 wherein the name-server-directory node, second DNS servers are global server load balancing (GSLB) directory nodes.
 40. The non-transitory machine readable medium of claim 39, wherein the name-server, third DNS servers are GSLB nodes.
 41. The non-transitory machine readable medium of claim 30, wherein each GSLB node provides a load balancing service for a set of server clusters. 